FIX: Props containing "key" prop is being spread into JSX #4563
Conversation
|
Is this going to be merged? Or is there a workaround? |
|
Hey @kyng-cytro, unfortunately it doesn't look like it as there are other PR's waiting a long time, I recommend checking out patch-package to workaround for yourself, and the best thing is that if/when it does get fixed patch-package will tell you and you simply delete the patch file. |
|
This lib is getting annoying to work with, and PRs that resolve issues are not merged, or at least they don't get any feedback |
|
Actually, turns out this change was merged (although not in isolation or from an existing PR) I will close this now as it is no longer needed and I can confirm it works without warning on the latest version. 77d3af7#diff-54d07d0dd9a891cd54e08e7642d895b92a592e9294af566460fa17dab475fa0eL363 |
4 participants
Destructure the key and pass it directly to the Touchable component to resolve error
Related issue
Fixes #4562
Test plan
I struggled to get react-native or expo upgraded to the latest versions in the example folder as it is quite out of date. Please see issue to understand the error thrown by react-native 0.76